What's New in Release 14.8.1 & 14.8.2
August 20, 2025
Testing environment for release 14.8.1 & 14.8.2
-
Google Chrome: Version 138.0.7204.184 (Official Build) (64-bit)
-
Microsoft Edge: Version 139.0.3405.86 (Official build) (64-bit)
-
Configuration: Windows 11 Enterprise
-
OS Build: 22631.5624
-
Experience: Windows Feature Experience Pack 1000.22700.1106.0
New revenue adjustment descriptions
We added two new adjustment descriptions, "Motor Vehicle" and "Interest."
Claim Batch process failure status
When a claim batch export fails during the SFTP step and is not received by the clearinghouse, a "Submission failed" message will appear in the "Submission Status" column on the Claim Batches page. The "Submission complete" status will display only if all export processes run successfully.
To filter the search to display only those with a failed status, click the box under the "Submission status" column heading and start typing "failed."
To view the reason for the failure, click the batch number. You will notice that any remaining processes did not run after the failure.
To try the failed process again, click the "Re-upload batch" button. If re-uploading does not work, contact ZOLL Support for help.
Denial color on the Dashboard changed
The denial color on the Dashboard has changed to vivid red color to standout and draw your attention.
Underscore character in profit center names
The underscore character '_' is now allowed in profit center names.
Ability to remove claims from a "Suspension - Payment plan disable" state
Before this release, an account could not be released from a suspended state - payment plan disabled state. Users would need to wait the number of days configured in Settings > Automated payment plan section.
Now users can release the suspension from the account and then from the claim.
Once the suspension is removed, the account can be placed back on a payment plan and the claim can be queued for submission.
Additional error information for NEMSIS imports
When a NEMSIS file fails to import due to a content issue, an error message is generated with details about the failure.
If you are monitoring the Dashboard, a failed import message appears in the top-left corner of the page. This message is a link to the Imported Claims page.
On the Imported Claims page, a "Not imported: file failed validation" message will display under the Import Status column.
To troubleshoot this issue, click the information icon. A pop-up message will display the line number and position of the issue. Only one issue appears in this window, as the software stops validating the file after the first error.
Click the Imported File link to view the file. Find the line number and position (the amount of characters from the left on that line).
Note: To see the line numbers for the import file:
Do a Ctrl+a to capture the content of the file
Open an app like Notepad ++ (this app shows the line numbers)
Do a Ctrl+v to copy the content of the file to the app
After fixing the issue, try importing the file again. Because the validation process stops at the first error, it is possible that there are additional errors that maybe uncovered when the file is re-imported. If additional errors are uncovered, use the steps outlined above to fix the issue.
Patient merging change
When two patient accounts are merged, a new account is created. Previously, PCS information and authorizations were not carried over during the merge. Now all PCS and authorizations from both accounts are included in the new patient record.
Ignore ePayment.50 setting option
There is a new setting option in the Configuration tab under the Integrations section that allows you to ignore ePayment.50 in the NEMSIS import file when setting the level of service. This setting is unchecked by default. When selected, ZOLL Billing will not automatically set the level of service value on claims based on the NEMSIS ePayment.50 value (the Level of Service field will be blank on the "Level of service & diagnosis" tab).
CSV payers file available to download
There is now an option to download a csv file that shows all the payers configured in your company.
The link displays on the Payers page in the upper right corner. Click the link to download the file to your PC and then open the file in your downloads folder.
The csv file will show only enabled and ZOLL payers and will include the following columns of information:
Payer | Benefit plans | Policy |
---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||
| ||
| ||
| ||
|
Settings | |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Mult-company Management
Hint: To identify all linked payers, try sorting by alphabetical order followed by filtering by payer or company.
|
|
|
The following issues were fixed in release 14.8.1 & 14.8.2:
On the Payers page > Edit Payer > Policy and Benefit Plan Requirement - The “Zip code in prior auth (2300 REF)” setting was not working with electronic clearinghouse submissions.
The billed date value was not being set for facility submissions which caused two aging reports to not include facility claims.
When an imported line item triggered a "Review Required" flag, the subsequent line items were not imported correctly.
NEMSIS files with loaded miles and mileage charge units greater than the amount allowed on a claim (9,999.9) were being allowed to import into ZOLL Billing. Now, if the imported mileage calculation (the difference between eResponse.21 and eResponse. 20) is greater that 9.999.9 miles, the import will fail. On the Imported Claims page, the information for the failed import will read " Mileage calculation (difference between eResponse.21 and eResponse .20) exceeds 9.999.9."
The payments shown in the Accounting Period Summary report was not matching the payments section in the accounting period.
Users were unable to create a claim for a patient created in Admin > Billing > Patients. Note: You are still unable to create claims via a NEMSIS API import for patients created in Admin.
Hotfixes:
Attempting to add an account note from a claim was producing a system error.
Mileage Charge Contractuals were not being applied properly if a facility had contracted charges that were set to flat amount per HCPCS with the same price per unit in multiple charge categories.
The "Download reports" option for multiple closed accounting periods was failing.
When users updated or changed the Eligibility check value in MCM child company payer entries, they unlinked from the patent company. This hotfix updated the MCM payer linking process so that when a payer with an existing value in the "Eligibility Checks" field was updated, it remained linked. Additionally, any payers that were previously ulinked were matched and re-linked.